RAID devices, systems, and methods

ABSTRACT

The invention is directed to a storage device utilizing laptop storage drives and rackmount server adapted to use the same. The storage device includes a body and drive software. The drive and internal portions of the body are adapted to form contact fits. The software of the storage device provides an electronic interface that permits operations of advantageous RAID configurations.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 14/816,541, filed Aug. 3, 2016, now U.S. Pat. No. 9,519,434, which claims priority to U.S. patent application Ser. No. 12/851,870, now U.S. Pat. No. 9,134,771, both of which are hereby incorporated by reference herein in their entireties.

FIELD OF THE INVENTION

The present invention relates to the field of variable electronic storage systems and more specifically to the field of Redundant Arrays of Independent Disks systems.

BACKGROUND

It is known how to store data in an array of disks managed by an array controller to control the storage and retrieval of data from the array is known. One example of such a system is a Redundant Array of Independent Disks (RAID) comprising a collection of multiple disks organized into a disk array managed by a common array controller. The array controller presents the array to the user as one or more virtual disks. Disk arrays are the framework to which RAID functionality is added in functional levels to produce cost-effective, high-performance disk systems having varying degrees of reliability based on the type of RAID architecture implemented. RAID architecture can be conceptualized in two dimensions as individual disks arranged in adjacent columns. Typically, each disk is partitioned with several identically sized data partitions known as stripes, or minor stripes. Distributed across the array of disks in rows, the identically sized partitioned strips form a data stripe across the entire array of disks. Therefore, the array contains stripes of data distributed as rows in the array, wherein each disk is partitioned into stripes of identically partitioned data and only one strip of data is associated with each stripe in the array.

As is known, RAID architectures have been standardized into several categories. RAID level 0 is a performance-oriented striped data mapping technique incorporating uniformly sized blocks of storage assigned in a regular sequence to all of the disks in the array. RAID level 1, also called mirroring, provides simplicity and a high level of data availability, but at a relatively high cost due to the redundancy of the disks. RAID level 3 adds redundant information in the form of parity data to a parallel accessed striped array, permitting regeneration and rebuilding of lost data in the event of a single-disk failure. RAID level 4 uses parity concentrated on a single disk to allow error correction in the event of a single disk failure, but the member disks in a RAID 4 array are independently accessible. In a RAID 5 implementation, parity data is distributed across some or all of the member disks in the array. The RAID 5 architecture achieves performance by striping data blocks among N disks, and achieves fault-tolerance by using 1/N of its storage for parity blocks, calculated by taking the exclusive-or (XOR) of all data blocks in the parity disks row. A RAID 6 architecture is similar to RAID 5, but RAID 6 can overcome the failure of any two disks by using an additional parity block for each row (for a storage loss of 2/N). In one example of a RAID 6 architecture, the first parity block (P) is calculated with XOR of the data blocks. The second parity block (Q) employs Reed-Solomon codes. One drawback of the known RAID 6 implementation is that it requires a complex and computationally time-consuming array controller to implement the Reed-Solomon codes necessary to recover from a two-disk failure. The complexity of Reed-Solomon codes may preclude the use of such codes in software, or may necessitate the use of expensive special purpose hardware. Thus, implementation of Reed-Solomon codes in a disk array increases the cost, complexity, and processing time of the array.

SUMMARY

The invention is directed to a storage device having a body, drive software, and an interface. The body includes at least two interior drive slots with an internal support member. Multiple laptop storage drives having a girth of less than 2.5 includes fit within each slot. The drives include an external drive fit member adapted to form a contact fit relationship with the internal support member. The body includes a drive door for each drive adapted to fit within the body. The software provides an electronic interface that permits operations of RAID 0, RAID 1, non-RAID, and combinations thereof. The body includes a physical interface that includes, and preferably consists of, a power indicator.

Another embodiment of the storage device includes a body with a single interior slot with at least four of the laptop storage drives of girth less than 2.5 inches in a storage drive array The drives include an external drive fit member adapted to form a contact fit relationship with the internal support member. The body includes a drive door for each drive adapted to fit within the body. The software provides an electronic interface that permits operations of RAID 0, RAID 1, RAID 5, and combinations thereof. The body includes a physical interface that includes, and preferably consists of, a power indicator.

The present invention further includes rackmount servers adapted to accept the storage devices, and a system that includes a computer in electronics communication with the storage devices directly or via a rackmount server.

These aspects of the invention are not meant to be exclusive. Furthermore, some features may apply to certain versions of the invention, but not others. Other features, aspects, and advantages of the present invention will be readily apparent to those of ordinary skill in the art when read in conjunction with the following description, and accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a perspective view of the device of the present invention.

FIG. 2 is a perspective view of the device of the present invention.

FIG. 3 is a perspective view of the server of the present invention.

FIG. 4 is a plan view of the device of the present invention.

FIG. 5 is a perspective view of the device of the present invention.

FIG. 6 is a perspective view of the device of the present invention.

FIG. 7 is a perspective view of the server of the present invention.

FIG. 8 is a view of the process of the present invention.

FIG. 9 is a view of the system of the present invention.

FIGS. 10A-10D are cutaway, partial views of the device of the present invention.

DETAILED DESCRIPTION

Referring first to FIG. 1 and FIG. 8, a basic embodiment of the storage device 100 and variable storage process 200 are shown. The device 100 preferable includes two or more 2.5″ formatted SATA hard drives 102. The drives 102 are removably positioned within drive slots 104 dimensioned to accept the drives 102 within the device body 106. The drive slots 104 may occupy any position, but a preferred position places one drive on top of another as is shown by FIG. 5. Each slot, 104, can only accept one hard drive. It is preferred that the two slots 104 are separated by a thin sheet of metal as depicted in FIG. 10D. The preferred slot includes internal body fit members as support means. By body fit members, it is meant that rather than rely on quasi-permanent means of component attachment that requires actuating of distinct attachment accessories, e.g. bolts and screws, the present invention utilizes components that rely on contact to secure two components.

Turning now to FIGS. 10A-10D, the preferred body fit members 190 within the drive slots 104 include siderails or some other internal support means 192 that position the drive slot in a position proximate to the drive so as to provide fit support. The drive slot may include a single continuous opening that utilizes the body fit members to form any desired physical partitions. The internal body fit member of the device may include a body shelf, siderails, a door shelf, snaps, grooves, etc. The external drive fit members 194 may include a drive 102 with a body having dimensions to releasably mate with the internal body fit members of the device. The fittings may form a rest fit relationship such that the drive merely rests upon a body fit member. The fittings may form a close fit relationship, such that a close sizing between a portion of the drive or component thereof and the body slot or a component thereof forms a near fit. By near fit, it is meant that a distance between two components is highly minimized to a substantial degree dictated by the natural size tolerances between two components. The fittings may form an interference fit, such that one component includes a size adapted to require pressure to fit within a second component and upon fitting requires substantial pressure for removal. The fit members serve as a means of support in addition to the natural support provided by any internal data couplings 196 within the device body, e.g. eSATA ports. Returning to FIG. 1, a user need only open the slot door 108 to access the disk 102 for removal.

Turning now to FIG. 2, there are preferably three connections, located on the rear of the body. The connections include two data connections, including a USB 2.0 port 110 and an eSATA 3.0 Gb/s port 112. When the device is used via the USB Port, the drives will not be capable of removal during operation; when the device is used with the eSATA port, the drives will be capable of removal during operation. Additionally, the device 100 includes a direct current port 114. The body 106 preferably includes venting 116 to permit the emission of heat.

With reference to FIGS. 8 and 9, the setup and configuration of the system 500, which includes device(s) 100, the supporting computer 300 in communication with the device(s) 100, and potentially one or more rackmount servers bearing the devices 100 will by performed via software 600 loaded onto the computer 300 that connects to the device directly or through a rackmount server. The process 200 of the present invention includes recognition and configuration of the device. Upon insertion of a new hard drive in either the primary or ancillary slot, the device 100 will remain dormant 202, 204 and take no action. For the purposes of the present disclosure, the primary disk shall refer to the base drive positioned in the device, whereas the ancillary drive shall refer to any other number of drives described either by their relationship to either the primary drive or another ancillary drive. Each drive includes drive software 700 having a recognition token that includes two parameters: a recognition parameter identifies the drive as capable of use with the present invention, and an action parameter that includes an action request. The preferred action request includes instructions to remain dormant until instructions from the software are accepted. An alternative action request includes immediate configuration by the computer without user interaction. The recognition token is recognized by software within a computer adapted to seek the recognition token actively. The computer 300 informs the user of the existence of a new drive 206, 208 and requests an initiation action 210, 212 for the drive. Specifically, the computer provides a two-pronged decision to the user as to whether s/he would prefer operation of the device as a RAID 0 configuration 218, a RAID 1 configuration 220, or operate as a dual hard drive 216. Other forms of the present invention my present other raid options, such as RAID 5.

Turning now to FIGS. 3 and 4, the present invention further includes a rackmount server 400 bearing multiple storage devices 100. The server 400 includes a server body 402 with multiple device slots 410 dimensioned to accept the storage devices 100. The embodiment of the storage device 100 adapted for use with the rackmount server 400 includes direct current contact points 124 rather than use of a direct current plug outlet. The preferred rackmount server 400 includes an optical drive 406 and multiple 2.5″ SATA hard drives for the operation of the server itself. Any drive 102 within the rackmount server 400 may be removed and still be capable of backing up any number of servers on a local area network. The software that that operates the device 100 is the same software that operates the server 400, and preferably includes functions such that the only physical interface required upon the drive or rackmount server body is a power indicator 404. The server 400 operates a server operating system and backup software.

Turning now to FIGS. 5-7, the present invention further includes a quad-drive embodiment of the device 100 and an embodiment of the rackmount server 400 adapted to internally support multiple quad-drive devices 100. The quad-drive may include either direct current contacts for positioning within the rackmount server 400 or a direct current plug outlet. It is preferred that the server 400 include a rechargeable power source. The preferred operation utilizes the quad-drive embodiment of the device 100 and the server 400 adapted therefor to be software configurable only. Both the device 100 and server run in RAID 5 mode only. Furthermore, the server 400 must possess at least three drives 102 therein to be configured for operation. Any other drive 102 may be part of the RAID 5 or can be a “hot spare.”

Although the present invention has been described in considerable detail with reference to certain preferred versions thereof, other versions would be readily apparent to those of ordinary skill in the art. Therefore, the spirit and scope of the appended claims should not be limited to the description of the preferred versions contained herein. 

What is claimed is:
 1. A RAID storage device, comprising: a first storage drive; a second storage drive; and a processor that sends a recognition token to a computing device, wherein the recognition token identifies the RAID storage device, wherein the processor receives a communication from the computing device requesting initiation of the RAID storage device.
 2. The RAID storage device of claim 1, wherein the processor sends the recognition token in response to a request from the computing device.
 3. The RAID storage device of claim 1, wherein the processor sends a first recognition token and a second recognition token, wherein the first recognition token identifies the first storage drive and the second recognition token identifies the second storage drive.
 4. The RAID storage device of claim 1, wherein the recognition token comprises a recognition parameter that identifies at least one of the storage drives as being compatible with the computing device.
 5. The RAID storage device of claim 1, wherein the recognition token comprises an action parameter comprising instructions for the storage device to remain dormant until receiving instructions, from the computing device, to initialize.
 6. The RAID storage device of claim 1, wherein the processor sends the recognition token to the computing device automatically upon the RAID storage device establishing electronic communication with the computing device.
 7. The RAID storage device of claim 1, wherein the communication includes a request for initiation of the RAID storage device according to a configuration.
 8. The RAID storage device of claim 7, wherein the configuration is at least one of a RAID 0 configuration, RAID 1 configuration, dual hard drive configuration, and combinations thereof.
 9. A storage device, comprising: a plurality of storage drives; and a processor that executes instructions contained on a non-transitory, computer-readable storage medium, the instructions causing the processor to: establish communication between the processor and an external computing device; and send, from the processor to the external computing device, a recognition token identifying the storage device, wherein the processor sends a request to the external computing device for initiation instructions.
 10. The storage device of claim 9, wherein the processor sends the recognition token in response to a request from the external computing device.
 11. The storage device of claim 9, wherein sending the recognition token comprises sending a plurality of recognition tokens, wherein each of the plurality of recognition tokens identifies one of the plurality of storage drives.
 12. The storage device of claim 9, wherein the recognition token comprises a recognition parameter that identifies at least one of the plurality of storage drives as being compatible with the external computing device.
 13. The storage device of claim 9, wherein the recognition token comprises an action parameter comprising instructions for the storage device to remain dormant until receiving instructions, from the external computing device, to initialize.
 14. The storage device of claim 9, wherein sending the recognition token to the external computing device is carried out automatically upon placing the storage device in electronic communication with the external computing device.
 15. The storage device of claim 9, wherein the request includes a request for a user of the external computing device to select a configuration.
 16. The storage device of claim 15, wherein the request for the user of the external computing device to select a configuration includes a request to select at least one of a RAID 0 configuration, RAID 1 configuration, dual hard drive configuration, and combinations thereof.
 17. A storage device, comprising: a plurality of storage drives; and a processor that executes instructions contained on at least one of the plurality of storage drives, the instructions causing the processor to: establish communication between the processor and an external computing device; send, from the processor to the external computing device, a recognition token identifying the storage device; and receive a communication from the external computing device requesting initiation of the storage device. 